Transmit power control command for transmission power adjustment

ABSTRACT

Apparatuses, methods, and systems are disclosed for receiving a transmit power control command for transmission power adjustment. One method includes monitoring a feedback channel. The feedback channel includes: feedback information corresponding to a data transmission from a remote unit to a network unit; and a transmit power control command including information for the remote unit to adjust a transmission power for subsequent data transmissions to the network unit.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/146,471 filed on Sep. 28, 2018, which claims priority to U.S. PatentApplication Ser. No. 62/564,803 entitled “TPC FOR PUSCH IN AUTONOMOUSUPLINK TRANSMISSIONS” and filed on Sep. 28, 2017 for Alexander JohannMaria Golitschek Edler von Elbwart, which is incorporated herein byreference in its entirety.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to transmit power controlcommand for transmission power adjustment.

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description: Third GenerationPartnership Project (“3GPP”), 5^(th) Generation (“5G”),Positive-Acknowledgment (“ACK”), Access Point (“AP”), Autonomous Uplink(“AUL”), Binary Phase Shift Keying (“BPSK”), Buffer Status Report(“BSR”), Carrier Aggregation (“CA”), Clear Channel Assessment (“CCA”),Cyclic Delay Diversity (“CDD”), Code Division Multiple Access (“CDMA”),Control Element (“CE”), Closed-Loop (“CL”), Coordinated Multipoint(“CoMP”), Cyclic Prefix (“CP”), Cyclical Redundancy Check (“CRC”),Channel State Information (“CSI”), Common Search Space (“CSS”), ControlResource Set (“CORESET”), Discrete Fourier Transform Spread (“DFTS”),Downlink Control Information (“DCI”), Downlink (“DL”), DemodulationReference Signal (“DMRS”), Downlink Pilot Time Slot (“DwPTS”), EnhancedClear Channel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”),Evolved Node B (“eNB”), Effective Isotropic Radiated Power (“EIRP”),European Telecommunications Standards Institute (“ETSI”), Frame BasedEquipment (“FBE”), Frequency Division Duplex (“FDD”), Frequency DivisionMultiple Access (“FDMA”), Frequency Division Orthogonal Cover Code(“FD-OCC”), General Packet Radio Services (“GPRS”), Guard Period (“GP”),Global System for Mobile Communications (“GSM”), Hybrid Automatic RepeatRequest (“HARQ”), International Mobile Telecommunications (“IMT”),Internet-of-Things (“IoT”), Layer 2 (“L2”), Licensed Assisted Access(“LAA”), Load Based Equipment (“LBE”), Listen-Before-Talk (“LBT”),Logical Channel (“LCH”), Logical Channel Prioritization (“LCP”), LongTerm Evolution (“LTE”), Multiple Access (“MA”), Medium Access Control(“MAC”), Multimedia Broadcast Multicast Services (“MBMS”), Modulationand Coding Scheme (“MCS”), Machine Type Communication (“MTC”), massiveMTC (“mMTC”), Multiple Input Multiple Output (“MIMO”), Maximum PowerReduction (“MPR”), Multi User Shared Access (“MUSA”), Narrowband (“NB”),Negative-Acknowledgment (“NACK”) or (“NAK”), Next Generation Node B(“gNB”), New Data Indicator (“NDI”), Non-Orthogonal Multiple Access(“NOMA”), New Radio (“NR”), Orthogonal Frequency Division Multiplexing(“OFDM”), Open-Loop (“OL”), Power Angular Spectrum (“PAS”), PowerControl (“PC”), Primary Cell (“PCell”), Physical Broadcast Channel(“PBCH”), Physical Downlink Control Channel (“PDCCH”), Packet DataConvergence Protocol (“PDCP”), Physical Downlink Shared Channel(“PDSCH”), Pattern Division Multiple Access (“PDMA”), Physical HybridARQ Indicator Channel (“PHICH”), Power Headroom (“PH”), Power HeadroomReport (“PHR”), Physical Layer (“PHY”), Physical Random Access Channel(“PRACH”), Physical Resource Block (“PRB”), Physical Uplink ControlChannel (“PUCCH”), Physical Uplink Shared Channel (“PUSCH”), QuasiCo-Located (“QCL”), Quality of Service (“QoS”), Quadrature Phase ShiftKeying (“QPSK”), Radio Access Network (“RAN”), Radio Access Technology(“RAT”), Resource Block Assignment (“RBA”), Radio Resource Control(“RRC”), Random Access Procedure (“RACH”), Random Access Response(“RAR”), Radio Link Control (“RLC”), Radio Network Temporary Identifier(“RNTI”), Reference Signal (“RS”), Remaining Minimum System Information(“RMSI”), Resource Spread Multiple Access (“RSMA”), Reference SignalReceived Power (“RSRP”), Round Trip Time (“RTT”), Redundancy Version(“RV”), Receive (“RX”), Sparse Code Multiple Access (“SCMA”), SchedulingRequest (“SR”), Sounding Reference Signal (“SRS”), Single CarrierFrequency Division Multiple Access (“SC-FDMA”), Secondary Cell(“SCell”), Shared Channel (“SCH”), Sub-carrier Spacing (“SCS”), ServiceData Unit (“SDU”), Signal-to-Interference-Plus-Noise Ratio (“SINR”),System Information Block (“SIB”), Synchronization Signal (“SS”),Scheduled Uplink (“SUL”), Transport Block (“TB”), Transport Block Size(“TB S”), Time-Division Duplex (“TDD”), Time Division Multiplex (“TDM”),Time Division Orthogonal Cover Code (“TD-OCC”), Transmission PowerControl (“TPC”), Transmission Reception Point (“TRP”), Transmission TimeInterval (“TTI”), Transmit (“TX”), Uplink Control Information (“UCI”),User Entity/Equipment (Mobile Terminal) (“UE”), Uplink (“UL”), UniversalMobile Telecommunications System (“UMTS”), Uplink Pilot Time Slot(“UpPTS”), Ultra-reliability and Low-latency Communications (“URLLC”),and Worldwide Interoperability for Microwave Access (“WiMAX”).

In certain wireless communications networks, a transmit power controlcommand for transmission power adjustment may be used. In such networks,the transmit power control command may indicate to a remote unit how toadjust its transmission power.

BRIEF SUMMARY

Methods for receiving a TPC command for transmission power adjustmentare disclosed. Apparatuses and systems also perform the functions of theapparatus. One embodiment of a method includes monitoring a feedbackchannel. In such an embodiment, the feedback channel includes: feedbackinformation corresponding to a data transmission from a remote unit to anetwork unit; and a transmit power control command including informationfor the remote unit to adjust a transmission power for subsequent datatransmissions to the network unit.

One apparatus for receiving a TPC command for transmission poweradjustment includes a processor that monitors a feedback channel. Insuch an embodiment, the feedback channel includes: feedback informationcorresponding to a data transmission from a remote unit to a networkunit; and a transmit power control command including information for theremote unit to adjust a transmission power for subsequent datatransmissions to the network unit.

One method for transmitting a TPC command for transmission poweradjustment includes transmitting a feedback channel. In such anembodiment, the feedback channel includes: feedback informationcorresponding to a data transmission from a remote unit to a networkunit; and a transmit power control command including information for theremote unit to adjust a transmission power for subsequent datatransmissions to the network unit.

One apparatus for transmitting a TPC command for transmission poweradjustment includes a transmitter that transmits a feedback channel. Insuch an embodiment, the feedback channel includes: feedback informationcorresponding to a data transmission from a remote unit to a networkunit; and a transmit power control command including information for theremote unit to adjust a transmission power for subsequent datatransmissions to the network unit.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for transmitting and/or receiving a TPCcommand for transmission power adjustment;

FIG. 2 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for receiving a TPC command for transmissionpower adjustment;

FIG. 3 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for transmitting a TPC command fortransmission power adjustment;

FIG. 4 is a schematic block diagram illustrating one embodiment of afeedback channel;

FIG. 5 is a flow chart diagram illustrating one embodiment of a methodfor receiving a TPC command for transmission power adjustment; and

FIG. 6 is a flow chart diagram illustrating one embodiment of a methodfor transmitting a TPC command for transmission power adjustment.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,embodiments may take the form of a program product embodied in one ormore computer readable storage devices storing machine readable code,computer readable code, and/or program code, referred hereafter as code.The storage devices may be tangible, non-transitory, and/ornon-transmission. The storage devices may not embody signals. In acertain embodiment, the storage devices only employ signals foraccessing code.

Certain of the functional units described in this specification may belabeled as modules, in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom very-large-scale integration(“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such aslogic chips, transistors, or other discrete components. A module mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices or the like.

Modules may also be implemented in code and/or software for execution byvarious types of processors. An identified module of code may, forinstance, include one or more physical or logical blocks of executablecode which may, for instance, be organized as an object, procedure, orfunction. Nevertheless, the executables of an identified module need notbe physically located together, but may include disparate instructionsstored in different locations which, when joined logically together,include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different computer readable storage devices.Where a module or portions of a module are implemented in software, thesoftware portions are stored on one or more computer readable storagedevices.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number oflines and may be written in any combination of one or more programminglanguages including an object oriented programming language such asPython, Ruby, Java, Smalltalk, C++, or the like, and conventionalprocedural programming languages, such as the “C” programming language,or the like, and/or machine languages such as assembly languages. Thecode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (“LAN”) or a wide area network (“WAN”), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. The code may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

FIG. 1 depicts an embodiment of a wireless communication system 100 fortransmitting and/or receiving a TPC command for transmission poweradjustment. In one embodiment, the wireless communication system 100includes remote units 102 and network units 104. Even though a specificnumber of remote units 102 and network units 104 are depicted in FIG. 1,one of skill in the art will recognize that any number of remote units102 and network units 104 may be included in the wireless communicationsystem 100.

In one embodiment, the remote units 102 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), aerialvehicles, drones, or the like. In some embodiments, the remote units 102include wearable devices, such as smart watches, fitness bands, opticalhead-mounted displays, or the like. Moreover, the remote units 102 maybe referred to as subscriber units, mobiles, mobile stations, users,terminals, mobile terminals, fixed terminals, subscriber stations, UE,user terminals, a device, or by other terminology used in the art. Theremote units 102 may communicate directly with one or more of thenetwork units 104 via UL communication signals.

The network units 104 may be distributed over a geographic region. Incertain embodiments, a network unit 104 may also be referred to as anaccess point, an access terminal, a base, a base station, a Node-B, aneNB, a gNB, a Home Node-B, a relay node, a device, a core network, anaerial server, a radio access node, an AP, NR, or by any otherterminology used in the art. The network units 104 are generally part ofa radio access network that includes one or more controllerscommunicably coupled to one or more corresponding network units 104. Theradio access network is generally communicably coupled to one or morecore networks, which may be coupled to other networks, like the Internetand public switched telephone networks, among other networks. These andother elements of radio access and core networks are not illustrated butare well known generally by those having ordinary skill in the art.

In one implementation, the wireless communication system 100 iscompliant with NR protocols standardized in 3GPP, wherein the networkunit 104 transmits using an OFDM modulation scheme on the DL and theremote units 102 transmit on the UL using a SC-FDMA scheme or an OFDMscheme. More generally, however, the wireless communication system 100may implement some other open or proprietary communication protocol, forexample, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants,CDMA2000, Bluetooth®, ZigBee, Sigfoxx, among other protocols. Thepresent disclosure is not intended to be limited to the implementationof any particular wireless communication system architecture orprotocol.

The network units 104 may serve a number of remote units 102 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The network units 104 transmit DL communicationsignals to serve the remote units 102 in the time, frequency, and/orspatial domain.

In one embodiment, a remote unit 102 may be used for receiving a TPCcommand for transmission power adjustment. The remote unit 102 maymonitor a feedback channel. In such an embodiment, the feedback channelmay include: feedback information corresponding to a data transmissionfrom the remote unit 102 to a network unit 104; and a transmit powercontrol command including information for the remote unit 102 to adjusta transmission power for subsequent data transmissions to the networkunit 104. Accordingly, the remote unit 102 may be used for receiving aTPC command for transmission power adjustment.

In certain embodiments, a network unit 104 may be used for transmittinga TPC command for transmission power adjustment. In some embodiments,the network unit 104 may transmit a feedback channel. In such anembodiment, the feedback channel may include: feedback informationcorresponding to a data transmission from a remote unit 102 to thenetwork unit 104; and a transmit power control command includinginformation for the remote unit 102 to adjust a transmission power forsubsequent data transmissions to the network unit 104. Accordingly, thenetwork unit 104 may be used for transmitting a TPC command fortransmission power adjustment

FIG. 2 depicts one embodiment of an apparatus 200 that may be used forreceiving a TPC command for transmission power adjustment. The apparatus200 includes one embodiment of the remote unit 102. Furthermore, theremote unit 102 may include a processor 202, a memory 204, an inputdevice 206, a display 208, a transmitter 210, and a receiver 212. Insome embodiments, the input device 206 and the display 208 are combinedinto a single device, such as a touchscreen. In certain embodiments, theremote unit 102 may not include any input device 206 and/or display 208.In various embodiments, the remote unit 102 may include one or more ofthe processor 202, the memory 204, the transmitter 210, and the receiver212, and may not include the input device 206 and/or the display 208.

The processor 202, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 202 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 202 executes instructions stored in thememory 204 to perform the methods and routines described herein. Invarious embodiments, the processor 202 may monitor a feedback channel.In such embodiments, the feedback channel may include: feedbackinformation corresponding to a data transmission from a remote unit 102to a network unit 104; and a transmit power control command includinginformation for the remote unit 102 to adjust a transmission power forsubsequent data transmissions to the network unit 104. The processor 202is communicatively coupled to the memory 204, the input device 206, thedisplay 208, the transmitter 210, and the receiver 212.

The memory 204, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 204 includes volatile computerstorage media. For example, the memory 204 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 204 includes non-volatilecomputer storage media. For example, the memory 204 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 204 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 204 also stores program code and related data, such as anoperating system or other controller algorithms operating on the remoteunit 102.

The input device 206, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 206 maybe integrated with the display 208, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device206 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 206 includes two ormore different devices, such as a keyboard and a touch panel.

The display 208, in one embodiment, may include any known electronicallycontrollable display or display device. The display 208 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 208 includes an electronic display capable of outputtingvisual data to a user. For example, the display 208 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display208 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 208 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 208 includes one or more speakersfor producing sound. For example, the display 208 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 208 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 208 may be integrated with the input device206. For example, the input device 206 and display 208 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 208 may be located near the input device 206.

The transmitter 210 is used to provide UL communication signals to thenetwork unit 104 and the receiver 212 is used to receive DLcommunication signals from the network unit 104, as described herein. Insome embodiments, the receiver 212 receives a feedback channel. Althoughonly one transmitter 210 and one receiver 212 are illustrated, theremote unit 102 may have any suitable number of transmitters 210 andreceivers 212. The transmitter 210 and the receiver 212 may be anysuitable type of transmitters and receivers. In one embodiment, thetransmitter 210 and the receiver 212 may be part of a transceiver.

FIG. 3 depicts one embodiment of an apparatus 300 that may be used fortransmitting a TPC command for transmission power adjustment. Theapparatus 300 includes one embodiment of the network unit 104.Furthermore, the network unit 104 may include a processor 302, a memory304, an input device 306, a display 308, a transmitter 310, and areceiver 312. As may be appreciated, the processor 302, the memory 304,the input device 306, the display 308, the transmitter 310, and thereceiver 312 may be substantially similar to the processor 202, thememory 204, the input device 206, the display 208, the transmitter 210,and the receiver 212 of the remote unit 102, respectively.

In certain embodiments, the transmitter 310 may transmit a feedbackchannel. In such an embodiment, the feedback channel includes: feedbackinformation corresponding to a data transmission from a remote unit 102to a network unit 104; and a transmit power control command includinginformation for the remote unit 102 to adjust a transmission power forsubsequent data transmissions to the network unit 104. Although only onetransmitter 310 and one receiver 312 are illustrated, the network unit104 may have any suitable number of transmitters 310 and receivers 312.The transmitter 310 and the receiver 312 may be any suitable type oftransmitters and receivers. In one embodiment, the transmitter 310 andthe receiver 312 may be part of a transceiver.

In AUL transmissions, a remote unit 102 may only receive DCI to enableand/or disable AUL. The DCI may include parameters for uplinktransmissions such as RBA and/or MCS. Thereafter, any AUL transmissionsare then done without new DCI whenever the remote unit 102 can access achannel and has data in its transmit buffer.

As may be appreciated, because relevant information for AUL is conveyedby an activation DCI, link adaptation such as MCS adjustment, powercontrol, RBA changes may only be possible by a new activation (orreactivation) DCI. In certain embodiments, TPC may be useful to react tofluctuating channel conditions that may be addressed by a differenttransmit power instead of MCS or RBA adaptation.

In various configurations, a “TPC for PUSCH” field that is available ina grant DCI for SUL transmissions cannot be used because of operationalcharacteristics of grant-free AUL transmission. In certainconfigurations, TPC commands as provided in LTE via DCI formats 3/3A oras provided in NR via DCI formats 2_2/2_3 cannot be transmitted on anunlicensed carrier because an unlicensed carrier doesn't carry a commonsearch space (or in other words, a remote unit 102 doesn't monitorcommon search space and corresponding DCI formats on an unlicensedcarrier). In some configurations, TPC commands for an unlicensed carrieras provided in LTE via DCI formats 3/3A or as provided in NR via DCIformats 2_2/2_3 cannot be conveyed by a licensed carrier, because DCIformats 3/3A in LTE or DCI formats 2_2/2_3 in NR do not support anycross-carrier indication or cross-carrier TPC adjustment.

In some embodiments, an SUL grant may be sent to a remote unit 102. TheSUL grant may include a “TPC for PUSCH field.” In such embodiments, aPDCCH resource may be used to convey the UL grant. In variousembodiments, an AUL transmission may be reactivated by a new DCI sent toa remote unit 102. The AUL transmission may include a “TPC for PUSCHfield.” In such embodiments, it may be implied that the TPC for PUSCHfield is not used and/or usable as a virtual CRC for protection againstAUL false activations.

In certain embodiments, transmission of DCI formats 3/3A or DCI formats2_2/2_3 may be enabled on an unlicensed carrier. In such embodiments,introduction and monitoring of a common search space on an unlicensedcarrier may be used. In some embodiments, cross-carrier signaling of TPCcommands via LTE DCI formats 3/3A or NR DCI formats 2_2/2_3 conveyed ona licensed carrier may be enabled. In such embodiments, an enhancementof LTE DCI formats 3/3A or NR DCI formats 2_2/2_3 as well ascorresponding RRC configuration enhancements may be used.

In various embodiments, a “TPC for PUSCH” field may be conveyed togetherwith (e.g., as part of) a HARQ-ACK feedback channel.

FIG. 4 is a schematic block diagram illustrating one embodiment of afeedback channel 400 (e.g., a HARQ-ACK feedback channel). Specifically,the feedback channel 400 includes feedback information 402 (e.g.,HARQ-ACK feedback) and a TPC command 404 (e.g., TPC command for PUSCH).The TPC command 404 may include any suitable number of bits that cantransmit the TPC command effectively. For example, the TPC command 404may include one bit, two bits, or more bits. In one embodiment, the TPCcommand 404 includes one bit. In such an embodiment, if the bit is “0,”the bit may indicate to not change the transmission power, or to reducethe transmission power (e.g., transmission power step down). Moreover,in such an embodiment, if the bit is “1,” the bit may indicate toincrease the transmission power (e.g., transmission power step up), orto not change the transmission power. In another embodiment, the TPCcommand 404 includes two bits. In such an embodiment, the two bits maybe used to indicate a transmission power step up (e.g., increase intransmission power), a transmission power step down (e.g., decrease intransmission power), no change of the transmission power, and/or atransmission power step up (or step down) with a different step sizethan indicated by another two-bit TPC command value.

Since AUL transmissions could be transmitted for any of a number ofconfigurable HARQ processes, a remote unit 102 may indicate via UCI forwhich HARQ ID a PUSCH is transmitted so that a network unit 104 canperform soft buffer combining and/or decoding. The UCI may also includean NDI field and an RV field.

In some embodiments, AUL supports transmission (e.g., a firsttransmission of a transport block) and retransmission (e.g.,transmissions after the first transmission of the same transport block).Therefore, some HARQ-ACK feedback mechanism from a network unit 104 to aremote unit 102 may be used that is similar to PHICH in licensedcarriers. In various embodiments, a new HARQ-ACK feedback channel (e.g.,the feedback channel 400) is transmitted on an unlicensed carrier, and,therefore, there may be no strict timing relation between a PUSCH and acorresponding HARQ-ACK feedback. In some embodiments, the new HARQ-ACKfeedback channel may convey multiple HARQ-ACK (e.g., for multiple recentAUL transmissions).

In certain embodiments, the new HARQ-ACK feedback channel may supportHARQ-ACK (e.g., the feedback information 402) for up to 16 HARQprocesses per remote unit 102, and may include one or two additional TPCbits (e.g., as in LTE DCI formats 3/3A, the TPC command 404). Theadditional TPC bits may add the TPC command 404 without much overhead.

In various embodiments, such as due to access to an unlicensed band, itmay be possible for UL transmissions to collide such that a network unit104 may not be able to detect an AUL transmission, even though a remoteunit 102 transmitted the AUL after successfully completing a clearchannel assessment. This may occur if a hidden node has transmitted at asame time as the remote unit 102, without the remote unit 102 noticingthe hidden node. Such an occurrence may result in the network unit 104receiving substantial noise and/or interference from the hidden node, sothat the network unit 104 is not aware of the AUL transmission. As aconsequence, the network unit 102 may be unaware that the remote unit102 expects a transmission of a HARQ feedback channel. In suchembodiments, regardless of the consequences for channel access (e.g.,contention window adjustment), the remote unit 102 may increase itstransmit power to make its transmissions more robust against possiblehidden node transmission. Thus, in certain embodiments, a remote unit102 may interpret a lack of a HARQ feedback channel within a definedtime-window after an AUL transmission as being equivalent to a “transmitpower step up” command.

In some embodiments, a remote unit 102 may receive a TPC command 404within a HARQ feedback command at the same time as receiving an uplinkgrant including a TPC field for a SUL transmission. In certainembodiments in which the remote unit 102 receives the TPC command 404and the TPC field in an UL grant, the remote unit 102 may process bothTPC commands simultaneously (e.g., effectively making two adjustments atthe same time). In other embodiments in which the remote unit 102receives the TPC command 404 and the TPC field in an UL grant, theremote unit 102 may only apply the TPC command received in the UL grant.In such embodiments, the remote unit may apply the TPC command receivedin the UL grant because the TPC command in the UL grant may be two bits,while the TPC command 404 in the HARQ feedback channel may be only onebit. As may be appreciated, a two bit TPC command may have bettergranularity and should therefore take precedence over a one bit TPCcommand. Accordingly, the TPC command 404 may be dropped and/or ignoredif a two bit TPC command is received in an UL grant.

FIG. 5 is a flow chart diagram illustrating one embodiment of a method500 for receiving a TPC command for transmission power adjustment. Insome embodiments, the method 500 is performed by an apparatus, such asthe remote unit 102. In certain embodiments, the method 500 may beperformed by a processor executing program code, for example, amicrocontroller, a microprocessor, a CPU, a GPU, an auxiliary processingunit, a FPGA, or the like.

The method 500 may include monitoring 502 a feedback channel. In someembodiments, the feedback channel includes: feedback informationcorresponding to a data transmission from a remote unit 102 to a networkunit 104; and a transmit power control command including information forthe remote unit 102 to adjust a transmission power for subsequent datatransmissions to the network unit 104.

In certain embodiments, the method 500 includes adjusting thetransmission power based on the transmit power control command. In someembodiments, the transmission power control command indicates atransmission power step up, a transmission power step down, or acombination thereof.

In various embodiments, the transmit power control command has a size of1 bit. In one embodiment, the 1 bit indicates a transmission power stepup or a transmission power step down.

In certain embodiments, the transmit power control command has a size of2 bits. In some embodiments, the 2 bits indicate at least onetransmission power step up and at least one transmission power stepdown.

In various embodiments, the method 500 includes performing atransmission power step up in response to not receiving acknowledgementof the previous data transmission within a predetermined time periodafter the previous data transmission. In one embodiment, the method 500includes performing a transmission power step up in response to beingunable to detect the feedback channel within a predetermined time periodafter a preceding autonomous uplink transmission. In certainembodiments, the method 500 includes transmitting the data transmissionfrom the remote unit 102 to the network unit 104.

FIG. 6 is a flow chart diagram illustrating one embodiment of a method600 for transmitting a TPC command for transmission power adjustment. Insome embodiments, the method 600 is performed by an apparatus, such asthe network unit 104. In certain embodiments, the method 600 may beperformed by a processor executing program code, for example, amicrocontroller, a microprocessor, a CPU, a GPU, an auxiliary processingunit, a FPGA, or the like.

The method 600 may include transmitting 602 a feedback channel. In someembodiments, the feedback channel includes: feedback informationcorresponding to a data transmission from a remote unit 102 to a networkunit 104; and a transmit power control command including information forthe remote unit 102 to adjust a transmission power for subsequent datatransmissions to the network unit 104.

In one embodiment, the transmission power control command indicates atransmission power step up, a transmission power step down, or acombination thereof. In certain embodiments, the transmit power controlcommand has a size of 1 bit. In some embodiments, the 1 bit indicates atransmission power step up or a transmission power step down.

In various embodiments, the transmit power control command has a size of2 bits. In one embodiment, the 2 bits indicate at least one transmissionpower step up and at least one transmission power step down. In certainembodiments, the method 600 includes receiving the data transmissionfrom the remote unit 102.

In one embodiment, a method comprises: monitoring a feedback channel,wherein the feedback channel comprises: feedback informationcorresponding to a data transmission from a remote unit to a networkunit; and a transmit power control command comprising information forthe remote unit to adjust a transmission power for subsequent datatransmissions to the network unit.

In certain embodiments, the method comprises adjusting the transmissionpower based on the transmit power control command.

In some embodiments, the transmission power control command indicates atransmission power step up, a transmission power step down, or acombination thereof.

In various embodiments, the transmit power control command has a size of1 bit.

In one embodiment, the 1 bit indicates a transmission power step up or atransmission power step down.

In certain embodiments, the transmit power control command has a size of2 bits.

In some embodiments, the 2 bits indicates a transmission power step up,a transmission power step down, no change in a transmission power, orsome combination thereof.

In various embodiments, the method comprises performing a transmissionpower step up in response to not receiving acknowledgement of theprevious data transmission within a predetermined time period after theprevious data transmission.

In one embodiment, the method comprises performing a transmission powerstep up in response to being unable to detect the feedback channelwithin a predetermined time period after a preceding autonomous uplinktransmission.

In certain embodiments, the method comprises transmitting the datatransmission from the remote unit to the network unit.

In one embodiment, an apparatus comprises: a processor that monitors afeedback channel, wherein the feedback channel comprises: feedbackinformation corresponding to a data transmission from the apparatus to anetwork unit; and a transmit power control command comprisinginformation for the apparatus to adjust a transmission power forsubsequent data transmissions to the network unit.

In certain embodiments, the processor adjusts the transmission powerbased on the transmit power control command.

In some embodiments, the transmission power control command indicates atransmission power step up, a transmission power step down, or acombination thereof.

In various embodiments, the transmit power control command has a size of1 bit.

In one embodiment, the 1 bit indicates a transmission power step up or atransmission power step down.

In certain embodiments, the transmit power control command has a size of2 bits.

In some embodiments, the 2 bits indicates a transmission power step up,a transmission power step down, no change in a transmission power, orsome combination thereof.

In various embodiments, the processor performs a transmission power stepup in response to not receiving acknowledgement of the previous datatransmission within a predetermined time period after the previous datatransmission.

In one embodiment, the processor performs a transmission power step upin response to being unable to detect the feedback channel within apredetermined time period after a preceding autonomous uplinktransmission.

In certain embodiments, the apparatus comprises a transmitter thattransmits the data transmission from the apparatus to the network unit.

In one embodiment, a method comprises: transmitting a feedback channel,wherein the feedback channel comprises: feedback informationcorresponding to a data transmission from a remote unit to a networkunit; and a transmit power control command comprising information forthe remote unit to adjust a transmission power for subsequent datatransmissions from the remote unit to the network unit.

In certain embodiments, the transmission power control command indicatesa transmission power step up, a transmission power step down, or acombination thereof.

In some embodiments, the transmit power control command has a size of 1bit.

In various embodiments, the 1 bit indicates a transmission power step upor a transmission power step down.

In one embodiment, the transmit power control command has a size of 2bits.

In certain embodiments, the 2 bits indicate a transmission power stepup, a transmission power step down, no change in a transmission power,or some combination thereof.

In some embodiments, the method comprises receiving the datatransmission from the remote unit.

In one embodiment, an apparatus comprises: a transmitter that transmitsa feedback channel, wherein the feedback channel comprises: feedbackinformation corresponding to a data transmission from a remote unit tothe apparatus; and a transmit power control command comprisinginformation for the remote unit to adjust a transmission power forsubsequent data transmissions from the remote unit to the apparatus.

In certain embodiments, the transmission power control command indicatesa transmission power step up, a transmission power step down, or acombination thereof.

In some embodiments, the transmit power control command has a size of 1bit.

In various embodiments, the 1 bit indicates a transmission power step upor a transmission power step down.

In one embodiment, the transmit power control command has a size of 2bits.

In certain embodiments, the 2 bits indicate a transmission power stepup, a transmission power step down, no change in a transmission power,or some combination thereof.

In some embodiments, the apparatus comprises a receiver that receivesthe data transmission from the remote unit.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

1. A method comprising: receiving a first transmission power control command and a second transmission power control command together; and applying only the first transmission power control command.
 2. The method of claim 1, wherein the first transmission power control command, the second transmission power control command, or a combination thereof are received in a physical downlink control channel.
 3. The method of claim 1, wherein the first transmission power control command, the second transmission power control command, or a combination thereof are received with information scheduling a physical uplink shared channel transmission.
 4. The method of claim 1, wherein the first transmission power control command is received with an uplink grant.
 5. The method of claim 4, wherein the first transmission power control command is received in a transmission power control field in the uplink grant.
 6. The method of claim 4, wherein the first transmission power control command comprises two bits.
 7. The method of claim 1, wherein the second transmission power control command is received within a feedback command.
 8. The method of claim 7, wherein the feedback command comprises a hybrid automatic repeat request feedback command.
 9. The method of claim 7, wherein the second transmission power control command comprises two bits.
 10. The method of claim 9, wherein the two bits indicate a transmission power step up or a transmission power step down.
 11. An apparatus comprising: a receiver that receives a first transmission power control command and a second transmission power control command together; and a processor that applies only the first transmission power control command.
 12. The apparatus of claim 11, wherein the first transmission power control command, the second transmission power control command, or a combination thereof are received in a physical downlink control channel.
 13. The apparatus of claim 11, wherein the first transmission power control command, the second transmission power control command, or a combination thereof are received with information scheduling a physical uplink shared channel transmission.
 14. The apparatus of claim 11, wherein the first transmission power control command is received with an uplink grant.
 15. The apparatus of claim 14, wherein the first transmission power control command is received in a transmission power control field in the uplink grant.
 16. The apparatus of claim 14, wherein the first transmission power control command comprises two bits.
 17. The apparatus of claim 11, wherein the second transmission power control command is received within a feedback command.
 18. The apparatus of claim 17, wherein the feedback command comprises a hybrid automatic repeat request feedback command.
 19. The apparatus of claim 17, wherein the second transmission power control command comprises two bits.
 20. The apparatus of claim 19, wherein the two bits indicate a transmission power step up or a transmission power step down. 